Skip to content

feat: apply CipherSuites to sing-box TLS outbounds - #4

Merged
patterniha merged 1 commit into
masterfrom
feat/cipher-suites-share-link
Jul 10, 2026
Merged

feat: apply CipherSuites to sing-box TLS outbounds#4
patterniha merged 1 commit into
masterfrom
feat/cipher-suites-share-link

Conversation

@patterniha

Copy link
Copy Markdown
Owner

Picks up a commit stranded on feat/cipher-suites-share-link: it was pushed right after #3 had already been merged, so it never landed in master (same situation as patterniha/PattNG#3 earlier).

What changed

sing-box supports cipher_suites on outbound TLS — a list of the same Go TLS names that Xray takes as a colon-separated string — so the CipherSuites setting no longer silently does nothing when a profile runs on the sing-box core (including TUIC/Anytls, where the field is editable).

  • Tls4Sbox: new cipher_suites field.
  • SingboxOutboundService.GenOutboundTls: maps the stored string (split on : or ,) in the TLS branch only; REALITY uses uTLS, where cipher suites don't apply.

Per sing-box docs, TLS 1.3 cipher suites are not configurable and the option is ignored for them; that's inherent to the option.

ServiceLib builds cleanly with this change (0 warnings, 0 errors).

🤖 Generated with Claude Code

sing-box supports cipher_suites on outbound TLS (a list of the same Go
TLS names Xray takes as a colon-separated string), so the setting no
longer silently does nothing when a profile runs on the sing-box core.

Add cipher_suites to Tls4Sbox and map it in GenOutboundTls for the TLS
branch only (REALITY uses uTLS where cipher suites do not apply),
splitting the stored string on ":" or ",".

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@patterniha
patterniha merged commit 5a8ec29 into master Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant